🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- candidate test file ---'
sed -n '1,80p' backend/src/tests/tests-iniciales.test.ts

printf '%s\n' '--- Jest configuration and package versions ---'
find . -maxdepth 3 -type f \( -name 'package.json' -o -iname '*jest*' -o -name 'tsconfig*.json' \) -print
rg -n --hidden --glob '!node_modules/**' \
  'jest|ts-jest|babel-jest|swc|transform|automock|PrismaClientInitializationError|singleMock|mockPrisma' \
  package.json backend/package.json backend 2>/dev/null | head -250

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 8617

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- backend package configuration ---'
cat backend/package.json

printf '%s\n' '--- backend TypeScript configuration ---'
cat backend/tsconfig.json

printf '%s\n' '--- repository Jest configuration files ---'
find . -maxdepth 4 -type f \( -iname 'jest.config.*' -o -iname 'jest.setup.*' -o -name '.babelrc' -o -name 'babel.config.*' \) -print

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 1862

🌐 Web query:

Jest 29 jest.mock module factory out-of-scope variables names beginning with mock ts-jest hoist-jest official documentation

💡 Result:

In Jest, calls to jest.mock are automatically hoisted to the top of the file [1][2][3]. Because of this hoisting, the code inside the module factory function is executed before the rest of the file's code, including variable initializations [1][3]. Consequently, accessing variables defined outside the factory is generally prohibited to prevent runtime errors caused by accessing uninitialized values [1][4][5]. To allow referencing variables within the mock factory, Jest provides an escape hatch: if a variable name begins with the word "mock" (case-insensitive), the babel-plugin-jest-hoist will permit its use inside the factory [1][4][5]. However, using this prefix does not automatically resolve the underlying issue of hoisting [1][3]. Even if the variable is permitted by the plugin, it remains your responsibility to ensure the variable is properly initialized by the time the factory function is executed [1][3]. If the variable is not yet initialized when the factory runs, you will encounter a ReferenceError [1][3]. Common approaches to handle this include: * Using a higher-order function: If you need to access a mock function, wrapping the reference in a function within the factory can delay the access until the mock is actually used, which may occur after initialization [1][6][3]. * Lazy initialization: Ensuring the mock is required or accessed lazily [4][5]. * Re-importing inside the factory: You can require or import dependencies directly inside the factory function to ensure they are available in that scope [6][7][8]. Regarding ts-jest, it performs its own hoisting logic to ensure compatibility with Jest's requirements [9][10]. While ts-jest aims to replicate this behavior, issues can arise depending on your configuration (e.g., if you disable built-in transformations or use certain module systems) [9][11]. If hoisting is not behaving as expected, ensure you are using the appropriate configuration (e.g., using babel-jest or the built-in ts-jest transformers) and follow the requirement to place jest.mock calls at the top level of the file [9][11].

Citations:

• 1: https://github.com/jestjs/jest/blob/main/docs/Es6ClassMocks.md
• 2: https://jestjs.io/docs/next/manual-mocks
• 3: https://jestjs.io/docs/es6-class-mocks
• 4: https://github.com/facebook/jest/blob/main/packages/babel-plugin-jest-hoist/src/index.ts
• 5: https://github.com/jestjs/jest/blob/main/packages/babel-plugin-jest-hoist/src/index.ts
• 6: The module factory of jest.mock() is not allowed to reference any out-of-scope variables jestjs/jest#2567
• 7: babel-plugin-jest-hoist: The module factory of jest.mock() is not allowed to reference any out-of-scope variables. jestjs/jest#9730
• 8: babel-plugin-jest-hoist: The module factory of jest.mock() is not allowed to reference any out-of-scope variables. jestjs/jest#9730
• 9: https://github.com/kulshekhar/ts-jest/wiki/Troubleshooting
• 10: https://github.com/kulshekhar/ts-jest/blob/master/src/transformers/hoist-jest.ts
• 11: [Bug]: jest.mock calls are not hoisted in CommonJS test suites kulshekhar/ts-jest#4280

🌐 Web query:

site:github.com/kulshekhar/ts-jest/blob v29.2.5 hoist-jest.ts out-of-scope variables jest.mock factory

💡 Result:

In ts-jest, specifically surrounding version 29.2.5, the hoisting mechanism—implemented in hoist-jest.ts—is designed to move jest.mock and related calls to the top of the file [1]. Because these calls are moved to the top of the scope, any variables referenced within the jest.mock factory function that were defined later in the file would become out-of-scope or result in a reference error [2]. To address this, ts-jest performs a static analysis check during the transformation process. It identifies variables used within the factory function and verifies if they are available at the hoisted location [2]. Key points regarding this behavior include: 1. Static Analysis: The transformer inspects the factory function of jest.mock to detect dependencies [1][2]. If it determines that the factory function relies on variables that are defined after the mock call, it may avoid hoisting that specific call to prevent runtime errors [2]. 2. Variable Naming Conventions: By convention and implementation, variables starting with mock (case-insensitive) are often ignored by this out-of-scope check [2]. This allows developers to define mock implementations or helpers without triggering hoisting restrictions [2]. 3. Factory API Refactor: Around the v29.x series, the codebase transitioned to using the TypeScript factory API for AST transformations [3][4]. This change improved the robustness and maintainability of the transformer, including the logic that handles hoisting and scope validation [3][4]. If you encounter an error related to out-of-scope variables, ensure that any dependencies used inside your jest.mock factory function are defined before the mock call or are globally available [2]. Alternatively, you can move the logic inside the factory function or define the necessary variables earlier in the test file [2].

Citations:

• 1: https://github.com/kulshekhar/ts-jest/blob/master/src/transformers/hoist-jest.ts
• 2: https://github.com/kulshekhar/ts-jest/blob/main/src/transformers/hoist-jest.spec.ts
• 3: https://github.com/kulshekhar/ts-jest/blob/v29.1.0/CHANGELOG.md
• 4: https://github.com/kulshekhar/ts-jest/blob/HEAD/CHANGELOG.md

🏁 Script executed:

#!/bin/bash
set -eu

url='https://raw.githubusercontent.com/kulshekhar/ts-jest/v29.2.5/src/transformers/hoist-jest.ts'
curl -fsSL "$url" | sed -n '1,240p'

printf '%s\n' '--- related ts-jest hoist tests ---'
test_url='https://raw.githubusercontent.com/kulshekhar/ts-jest/v29.2.5/src/transformers/hoist-jest.spec.ts'
curl -fsSL "$test_url" | rg -n -C 4 'mock|out.of.scope|prefix|hoist' | head -240

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 12672

🏁 Script executed:

#!/bin/bash
set -eu

python3 - <<'PY'
import json
from pathlib import Path

package = json.loads(Path("backend/package.json").read_text())
root = Path("backend")
config_files = [
    p for p in root.rglob("*")
    if p.is_file() and (
        p.name.startswith("jest.config.") or
        p.name.startswith("jest.setup.") or
        p.name in {".babelrc", "babel.config.js", "babel.config.cjs", "babel.config.json"}
    )
]

source = Path("backend/src/tests/tests-iniciales.test.ts").read_text()
print("test_command:", package["scripts"].get("test"))
print("ts-jest_dependency:", package["devDependencies"].get("ts-jest"))
print("jest_config_files:", [str(p) for p in config_files])
for identifier in ("PrismaClientInitializationError", "singleMock", "mockPrisma"):
    print(f"{identifier}_used_in_mock_factory:",
          identifier in source and (
              f"mockPrisma" == identifier or
              identifier in source[source.index("jest.mock('`@prisma/client`'"):source.index("// Mock de multer")] or
              identifier in source[source.index("jest.mock('multer'"):source.index("import { addCandidate")]
          ))
PY

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 381

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- candidate references ---'
rg -n -C 8 'diskStorageConfig|filename\s*:|destination\s*:|originalname|path\.join|path\.basename|sanitize|safe' backend/src backend/package.json package.json 2>/dev/null || true

printf '%s\n' '--- test context ---'
sed -n '280,375p' backend/src/tests/tests-iniciales.test.ts

printf '%s\n' '--- candidate file map ---'
fd -t f . backend/src | rg 'candidate|upload|multer|storage|config|test'

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 9628

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- upload service ---'
sed -n '1,140p' backend/src/application/services/fileUploadService.ts

printf '%s\n' '--- package versions and lock entries ---'
rg -n -C 3 '"multer"|"`@types/multer`"|multer@' backend/package.json package.json package-lock.json backend/package-lock.json yarn.lock pnpm-lock.yaml 2>/dev/null || true

printf '%s\n' '--- path construction probe ---'
node - <<'JS'
const path = require('node:path');

const destination = '../uploads/';
const originalname = '../../../../etc/passwd';
const generatedFilename = `1700000000000-${originalname}`;
const joined = path.join(destination, generatedFilename);
const resolved = path.resolve(destination, generatedFilename);

console.log(JSON.stringify({
  destination,
  originalname,
  generatedFilename,
  joined,
  resolved,
  escapesDestination: !resolved.startsWith(path.resolve(destination) + path.sep),
}, null, 2));
JS

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 3033

🌐 Web query:

Multer 1.4.5-lts.1 diskStorage _handleFile path.join(destination, filename) source

💡 Result:

In Multer 1.4.5-lts.1, the diskStorage engine uses the _handleFile method to process and save uploaded files [1][2]. Within this method, the destination directory and filename are resolved asynchronously using getDestination and getFilename functions [1][3]. Once both values are successfully retrieved, Multer constructs the full file path using path.join(destination, filename) [1][3]. This absolute or relative path is then passed to fs.createWriteStream to begin writing the file's contents from the incoming stream [1][3]. The core implementation logic in storage/disk.js is as follows [1]: DiskStorage.prototype._handleFile = function _handleFile (req, file, cb) { var that = this that.getDestination(req, file, function (err, destination) { if (err) return cb(err) that.getFilename(req, file, function (err, filename) { if (err) return cb(err) var finalPath = path.join(destination, filename) var outStream = fs.createWriteStream(finalPath) file.stream.pipe(outStream) outStream.on('error', cb) outStream.on('finish', function { cb(null, { destination: destination, filename: filename, path: finalPath, size: outStream.bytesWritten }) }) }) }) } Key observations regarding this process include: - Destination and Filename Resolution: Both getDestination and getFilename are either user-provided functions from the diskStorage options or default implementations [1]. If a string is provided for destination in the configuration, Multer internally wraps it in an adapter function to maintain a consistent interface [1][4]. - Write Stream: The file is written using Node.js's fs.createWriteStream. The resulting object passed to the callback includes the final path, destination, filename, and the file size [1][3]. - Orphan File Cleanup: Recent updates and maintenance (such as in version 1.4.5-lts.1 and related patches) include mechanisms to handle file cleanup, ensuring that if a request is aborted or truncated during the upload, partial files are not left as orphans on the disk [5].

Citations:

• 1: https://github.com/expressjs/multer/blob/master/storage/disk.js
• 2: https://app.unpkg.com/multer@1.4.5-lts.1/files/storage
• 3: https://readmex.com/en-US/expressjs/multer/page-5.1f7f84b21-df9c-4c61-a6b6-538b143a159e
• 4: fix(docs): handle string destination in storage engine template expressjs/multer#1394
• 5: expressjs/multer@c50a7e2

🏁 Script executed:

sed -n '320,370p' backend/src/tests/tests-iniciales.test.ts
printf '\n--- multer references ---\n'
rg -n "multerConfig|fileFilter|mimetype|originalname" backend/src backend -g '!node_modules' | head -200

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 4858

🏁 Script executed:

cat -n backend/src/application/services/fileUploadService.ts
printf '\n--- test setup ---\n'
sed -n '1,80p' backend/src/tests/tests-iniciales.test.ts
printf '\n--- upload call sites and routes ---\n'
rg -n "upload|fileUploadService|single\\(|array\\(|fields\\(|req\\.file|fileType" backend/src -g '*.ts'

Repository: LIDR-academy/AI4Devs-tdd-202607-seniors

Length of output: 8064